Notes/Domino Fix List
 |  |
| SPR # DKEY46APTZ | Fixed in 5.0a; 5.0.1 release |  |
Product Area: Technical Area: Server Platform: Cross Platform
SPR# DKEY46APTZ - Prevent a SCOS database from being damaged (losing its designation as the single copy object store) during compact. If you have a database which has been already damaged, please call Notes Support Services or go to www.support.lotus.com to obtain a tool to fix the database.
Technote Number: 1096760
Problem:
This issue was reported to Lotus Quality Engineering and has been addressed in
Domino 5.0a and 5.0.1.
Excerpt from the Lotus Notes and Lotus Domino Release 5.0a QMU and 5.0.1 QMR
fix list:
SPR# DKEY46APTZ - Prevent a SCOS database from being damaged (losing its
designation as the single copy object store) during compact. If you have a
database which has been already damaged, please call Notes Support Services or
go to http://www.ibm.com/software/lotus/support/ to obtain a tool to fix the
database. [5.0a, 5.0.1] (see below)
For Domino 5.0 or 5.0a customers, if you have already run R5 Compact on your
SCOS, use the appropriate platform-specific utility found in the document
titled "Utilities to Fix Single Copy Object Store (SCOS) that Has Been
Compacted Using Domino R5" (#21134 ) to reset the bit. Instructions for
running the utility are included in the document.
To avoid the problem, do not run R5 Compact on your SCOS database, even though
Lotus' upgrade instructions specifically recommend running Compact before
bringing up an R5 server.
Supporting Information:
Related Documents:
Utilities to Fix Single Copy Object Store (SCOS) that Has Been Compacted Using
Domino R5
Online Resource Document #: 21134 More >
Last Modified on 08/08/2001
Go back
|